Skip to content

bitcoind: fix raw TX fetching when using REST - #1006

Merged
tnull merged 2 commits into
lightningdevkit:mainfrom
jharveyb:2026-07-fix-getrawtx-rest
Aug 5, 2026
Merged

bitcoind: fix raw TX fetching when using REST#1006
tnull merged 2 commits into
lightningdevkit:mainfrom
jharveyb:2026-07-fix-getrawtx-rest

Conversation

@jharveyb

Copy link
Copy Markdown
Contributor

I noticed this issue while testing switching my nodes from the Electrum ChainSource to bitcoind.

An alternate fix here would also be to fetch the TX as binary instead of JSON - I can put up a PR for that if that's preferred.

@ldk-reviews-bot

ldk-reviews-bot commented Jul 27, 2026

Copy link
Copy Markdown

I've assigned @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

@ldk-reviews-bot
ldk-reviews-bot requested a review from tnull July 27, 2026 23:03
@tnull tnull added this to the 0.8 milestone Jul 28, 2026

@tnull tnull left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, good catch!

While you're here, mind adding a second commit that changes the range in random_chain_source to also cover the REST arm (i.e. should use 0..4 I believe), which would give us improved test coverage for the REST chain source?

@tnull tnull left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

The CI change showed that we have another bug in the REST client implementation. Landing this and working on a fix for it.

@tnull
tnull merged commit e7f9283 into lightningdevkit:main Aug 5, 2026
37 of 69 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants